bitkeeper revision 1.1159.1.226 (416c755eE9F1jcmOpMGr6aA5jVhyZg)

Merge ssh://srg//auto/groups/xeno/BK/xeno-unstable.bk
into equilibrium.research:/home/irchomes/mwilli2/xeno-docs.bk

diff --cc docs/user.tex
index d4c2fc126b0cc0855dcf18f4c10e6b38cbe87c11,96b8bfb1b621fbb37ce4a13e0e404fb60aed3500..8343175e503c87d1289fee4299ee6eb87fff0d21
--- 1/docs/user.tex
--- 2/docs/user.tex
+++ b/docs/user.tex
@@@ -423,13 -420,19 +423,19 @@@ title Xen 2.0 / XenLinux 2.6.8.
  \end{verbatim}
  
  The first line of the configuration (kernel...) tells GRUB where to
- find Xen itself and what boot parameters should be passed to it.  The
- second line of the configuration describes the location of the
+ find Xen itself and what boot parameters should be passed to it (in
+ this case, setting domain 0's memory allocation and the settings for
+ the serial port).
+ 
+ The second line of the configuration describes the location of the
  XenLinux kernel that Xen should start and the parameters that should
- be passed to it.
+ be passed to it (these are standard Linux parameters, identifying the
+ root device and specifying it be initially mounted read only and
+ instructing that console output be sent both to the screen and to the
+ serial port).
  
  As always when installing a new kernel, it is recommended that you do
 -not remove the original contents of \path{grub.conf} --- you may want
 +not remove the original contents of \path{menu.lst} --- you may want
  to boot up with your old Linux kernel in future, particularly if you
  have problems.